home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
kermit.columbia.edu
/
kermit.columbia.edu.tar
/
kermit.columbia.edu
/
newsgroups
/
misc.19941221-19950208
/
000464_news@columbia.edu_Wed Feb 8 08:06:33 1995.msg
< prev
Wrap
Internet Message Format
|
1995-07-31
|
2KB
Received: from apakabar.cc.columbia.edu by watsun.cc.columbia.edu with SMTP id AA24707
(5.65c+CU/IDA-1.4.4/HLK for <kermit.misc@watsun.cc.columbia.edu>); Wed, 8 Feb 1995 06:11:41 -0500
Received: by apakabar.cc.columbia.edu id AA02279
(5.65c+CU/IDA-1.4.4/HLK for kermit.misc@watsun); Wed, 8 Feb 1995 06:11:39 -0500
Newsgroups: comp.protocols.kermit.misc
Path: news.columbia.edu!panix!news.mathworks.com!udel!gatech!howland.reston.ans.net!ix.netcom.com!netcom.com!jzero
From: jzero@netcom.com (Jim Nakamura)
Subject: Re: Kermit is leaking
Message-Id: <jzeroD3o96y.K0I@netcom.com>
Organization: NETCOM On-line Communication Services (408 261-4700 guest)
References: <jzeroD35p9C.CAH@netcom.com> <3ggd7b$7km@apakabar.cc.columbia.edu> <jzeroD39uKJ.L63@netcom.com> <3h6365$fsr@source.asset.com>
Date: Wed, 8 Feb 1995 08:06:33 GMT
Lines: 22
Apparently-To: kermit.misc@watsun.cc.columbia.edu
weisek@source.asset.com (Kevin Weise) writes:
| Sorry I didn't get in on the beginning of this thread, so I don't know
| the execution environment. However, what it sounds like to me is PON
| over POTS (i.e., plain ol' noise over plain old telephone service). Are
| you using a modem and dialing over standard telephone lines? If so, it
| must be noise (esp. if the modem is more than a few years old), and
| Kermit is *not* the problem. More modern modems, esp. those with error-
| correction, do a terrific job of cleaning that nasty noise up, but only
| if they are talking with an equivalent error-correcting modem. If you
| are using a PC on an Ethernet link (with or without a terminal server),
| then I'm stumped as to what the problem could be.
Well I switched back to kermit (188) and the problem went away. The
problem only manifested itself on the "nn" newsreader anyway, so
I thought maybe there was an incommpatibility. :( I am using the
new USR 28.8 internal modem. Maybe that's the problem. :(
Oh well.
--
jzero@netcom.com